Jayton Posted January 23, 2010 Report Posted January 23, 2010 Righto, I installed VAG-COM on a Vista laptop, set VAG-COM to run as XP SP2 and to run as Administrator.I installed the cable and drivers, it came up as com37 (?!) at first, left it as that for the first test. I load the program up with the lead connected to the car, go to Options and test each of the ports, it comes up as working on com3. Cool I think, so go to try scan for faults using the Auto-scan, and it just goes over and over and over and doesn't appear to be able to find anything, it just keeps trying a higher address each time, the laptop battery ran out before it could complete (the battery/charge on it is pants!). So the next time after a bit of reading and changing the cable from com37 to com3 in device manager, I manually scan for the aux heater module faults and it can't find the module... great, so I scanned other modules and they can't be found either... I changed the com port to com1, com2 and com4 to see if that might help but VAG-COM still see's it as being com3 on each occasion?! What do you guys 'n gals think is wrong? The cable is a Quote
big_kev Posted January 24, 2010 Report Posted January 24, 2010 Ok start with the basics first. vista can be a bit twitchy with usb to serial adapters ( which is what your vagcom lead is....it is actually 2 devices a usb to serial adapter and a serial OBDII device......both contained in the one big bit at the end ). If you have access to the xp machine try using it first. Make sure that windows recognises the lead as a usb/serial adapter ( or similar ) and assigns a port that is not already in use ( com3 is usually ok....but not always ). Connect to vehicle ( ignition on....as this is what powers the OBDII device ). Make sure vagcom tests ok with port 3.....also check that it fails if you unplug it from the car. Do your first test on Module 01 as it will definitely recognise this if working correctly....some other modules may not be available or functioning correcty. If this still fails then either your lead is faulty or it is using the incorrect software drivers. As a footnote please be aware that Vista & Windows 7 will turn off USB devices by default to save power.....which obviously will stop your lead working.......this can be changed in device manager. Quote
Jayton Posted January 25, 2010 Author Report Posted January 25, 2010 Thanks for the tips. I tried with an XP laptop and vagcom wouldn't even see the lead <_< So I tried with another XP Laptop and vagcom again couldn't see the lead again, that was either both versions of the software (409.1s /serial and 409.1us /usb). But on the Vista laptop vagcom is recognising the lead while it's unplugged <_< Gee I could think of a million uses for a wireless usb lead :lol: I'm going to exchange the lead to see if that helps and steer clear of Vista when the new one comes. Quote
Jayton Posted January 25, 2010 Author Report Posted January 25, 2010 Oh should I have bought a KKL lead or other for an X reg MK2? Reason I ask is on a website selling similar leads it says for 2002+ models. Quote
big_kev Posted January 25, 2010 Report Posted January 25, 2010 The lead is exactly the same for the Mk1 & Mk2 galaxys. The problem you are having seems to be windows related rather than vagcom. You need to make sure that you are using the correct software/drivers for the lead. Most of the cheapo usb/serial leads use the ftdi chipset....see link below for generic drivers http://www.ftdichip.com/Drivers/VCP.htm Quote
Jayton Posted January 26, 2010 Author Report Posted January 26, 2010 Cheers Kev, I'll give those ago. I downloaded the two sets of drivers from another site, one was the set of drivers I got on the CD (the alternate version iirc) and the 'standard' set. Fingers crossed I get it working. Quote
Jayton Posted January 26, 2010 Author Report Posted January 26, 2010 I've been playing around with those drivers all night, vag-com 409.1s and 311.2n... still doing the same when I set the com port to say com1 in device manager and test com1 in vag-com, it will take longer to test than the other ports and return with the same error. port status: okinterface: not found and with 311.2n com port status: okinterface status: 3 - not found or not ready! :D Should have known it wouldn't have been easy... Quote
Jayton Posted January 28, 2010 Author Report Posted January 28, 2010 Having tried it on 4 computers now, with 3 versions of the software (311.2, 409.1s & 409.1us), 3 different drivers and getting the same results I've asked for a refund which I think is fair. Hopefully they agree and I get a new cable soon! Quote
samyuen Posted January 28, 2010 Report Posted January 28, 2010 Try this one! Go to www.keygen.us , search for (vag com). Download the 311.2. It worked on XP. Install the program with the download. Good Luck. Quote
Jayton Posted January 28, 2010 Author Report Posted January 28, 2010 Why? I've been using the legit software from the Ross Tech website... :D Quote
frogeye Posted January 29, 2010 Report Posted January 29, 2010 (edited) Hi, On my free trial vag com version, I have to click the 'Force dumb mode" box for my lead to work. Frogeye Edited January 29, 2010 by frogeye Quote
Jayton Posted January 29, 2010 Author Report Posted January 29, 2010 Got it working with the new drivers, I read elsewhere that vag-com should detect the cable without being plugged into the car with ign on... I went out to test it one last time with these new drivers and it worked :( Quote
big_kev Posted February 1, 2010 Report Posted February 1, 2010 I read elsewhere that vag-com should detect the cable without being plugged into the car with ign on... I went out to test it one last time with these new drivers and it worked :rolleyes: No it didn't :) The ODBII interface at the end of the lead recieves its power from the Car ignition feed.If its not plugged in then it does not exist to the computer or any other software. All that is being tested is that there is a working port on the computer. Quote
Rusty Nail Posted February 3, 2010 Report Posted February 3, 2010 Good evening all. I have had a similar experience with my VAG-COM. I bought a Quote
Jayton Posted February 3, 2010 Author Report Posted February 3, 2010 Run it as Administrator and change it to run in compatibility mode. If that doesn't work, delete VAG-COM (afaik it doesn't register itself so just delete it) and reinstall, also change the port to COM3, on my Googling for my problem I found people use COM3 in the end and it works. Quote
Rusty Nail Posted February 3, 2010 Report Posted February 3, 2010 Thanks Jayton. I will ive it a go a min and let you know what happens. Quote
Rusty Nail Posted February 3, 2010 Report Posted February 3, 2010 By jove - COM 3 does it again Thank you Jayton - now to find the open circuit glow plug and sort it out Cheers Quote
Jayton Posted February 3, 2010 Author Report Posted February 3, 2010 What order did you connect the car to the laptop? plug lead into laptop , start vag-com, start car, plug lead in car?plug lead into laptop , plug lead in car, start vag-com, start car? (the method I've used) I can't detect the aux heater and thus clear the code, I'm going to try what GSMGuy suggested here nexthttp://www.fordgalaxy.org.uk/ford/index.ph...x+heater+module Quote
Rusty Nail Posted February 3, 2010 Report Posted February 3, 2010 Hi JaytonThis is how I did it.... 1) Started the laptop2) Pluged the lead into the car3) Switched on the ignition4) Pluged into the laptop (make sure you always use the same USB port as you did when configuring the VAG-COM software and the com 3 setup)5) Start VAG-COM6) Perform test (should take only 1-2 seconds)7) Save8) Enter module 18 Mine took only a few seconds to register the module and be able to look at fault codes. I read the codes, printed them and also saved them Hope this helps mate Cheers :lol: Quote
Jayton Posted February 4, 2010 Author Report Posted February 4, 2010 Tried that and my normal method, still not detecting the module :lol: Quote
big_kev Posted February 4, 2010 Report Posted February 4, 2010 Tried that and my normal method, still not detecting the module :lol: Can you detect other modules .... ? Quote
Jayton Posted February 4, 2010 Author Report Posted February 4, 2010 (edited) Yeah, I scanned the engine and ABS and various other modules, cleared the DTC's and they haven't some back. I've just not been able to get into the aux heater module :lol: The fuse is a 7.5A (don't have heated seats so didn't put a 10A in) and the local motor factors didn't have a 5A in normal size only mini blade. Also, my cigar lighter and aux power sockets don't work, they have VE- but not VE+, could there be link? My aircon needs regassing I think because it flashes for a 10 seconds or so on start up, could it also indicate a problem with the aux heater? Edited February 4, 2010 by Jayton Quote
big_kev Posted February 4, 2010 Report Posted February 4, 2010 I've just not been able to get into the aux heater module :lol: Perfectly normal....don't worry about it. The early aux heaters ......probably all the Mk1's and maybe some of the early Mk2's have no communication to the aux heater module.And therefore it cannot be diagnosed using Vagcom ( or any other ).Probably just needs a new or cleaner glowplug....or maybe the fuel pump is knackered. You should be able to pick up a fault with your aircon unit flashing as this will show up using vagcom.It may be low pressure or could be something minor. Also is the fuse for your sockets under the drivers seat ? Quote
Jayton Posted February 4, 2010 Author Report Posted February 4, 2010 Not according to the Ford manual... I have the fusebox with 1-27(?) vertically and the rest below horizontally, with the 50+ range up top in mini blade format. I'll get a GP ordered in and hopefully that'll cure it! Quote
big_kev Posted February 4, 2010 Report Posted February 4, 2010 Not according to the Ford manual... I have the fusebox with 1-27(?) vertically and the rest below horizontally, with the 50+ range up top in mini blade format. Have you looked under the seat ? Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.